Minutes, IBIS Quality Committee

23 jan 2007

11-12 AM EST (8-9 AM PST)

ROLL CALL
  Adam Tambone
  Barry Katz
  Benny Lazer
  Benjamin P Silva
* Bob Ross, Teraspeed Consulting Group
  Brian Arsenault
* David Banas, Xilinx
* Eckhard Lenski
  Eric Brock
  Gregory R Edlund
  Hazem Hegazy
  John Figueroa
  John Angulo
  Katja Koller
  Kevin Fisher
* Kim Helliwell, LSI Logic
  Lance Wang
  Lynne Green
* Mike LaBonte, Cisco
* Moshiul Haque, Micron Technology
  Peter LaFlamme
  Radovan Vuletic, Qimonda
  Robert Haller
* Roy Leventhal, Leventhal Design & Communications
  Sherif Hammad
  Todd Westerhoff
  Tom Dagostino
  Kazuyoshi Shoji
  Sadahiro Nonoyama

Everyone in attendance marked by  *

NOTE: "AR" = Action Required.

-----------------------MINUTES ---------------------------
Mike LaBonte conducted the meeting.

AR Review:

- Kim finalize presentation for IBIS summit
  Done

- Mike change "exemption" to "exception" in the IQ spec.
  Done

New items:

Kim has had trouble viewing minutes files in Notepad. This is because
the files lack carriage returns. Associating .txt files with Worpad on
PCs fixes the problem.

Discussion:

We continued our review of IQ check 2.1 "IBIS file passes IBISCHK".
The guidelines for when the X designator should be used was discussed.
Mike felt that the X designator should be a flag indicating that the
file contains comments that should be seen before use. Kim pointed out
that we have to look into the file to see the IQ score anyway.

The basic policy is that ibischk should produce no error or warning
messages.  The only scenario under which using the X designator to make
an exception for an ibischk error would seem appropriate would be when
the error results from a parser bug.  Moshiul said he has seen a number
of these errors, and has resorted to commenting out otherwise valid
IBIS keywords to make the files pass ibischk. Most in the group felt
that the X designator was appropriate for this case. One suggestion
was to leave the "offending" keywords intact, in hopes that someday
ibischk would be fixed. But most felt that delivering a "broken" IBIS
file was not a good idea.

Another question was whether to use the X designator for ibischk
warnings. One opinion was that anyone taking the time to examine
the quality of an IBIS file should be able to clear up warnings,
and any that can not be resolved probably bear explanation.

We ended at the same point in the file as last time.

AR: Mike update 2.1 check to clarify recommendation.

Next meeting:

The next meeting is 2 weeks away to accomodate DesignCon attendees.

06 Feb 2007
11-12 AM EST (8-9 AM PST)
Phone: 1.877.384.0543 or 1.800.743.7560
ID: 2102026
Web access: http://meetingplace.cisco.com/join.asp?2102026

Meeting ended at 12:08 PM Eastern Time.